feat: add build-python-version output to reusable_tag_release#74
Merged
crowecawcaw merged 1 commit intoaws-deadline:mainlinefrom Apr 14, 2026
Merged
Conversation
Add a centralized build-python-version output (3.13) so that downstream repos can reference it in their PublishToPyPI jobs instead of hardcoding the Python version. This avoids breakage when build tools like hatchling drop support for older Python versions (hatchling 1.29.0 requires Python >=3.10). Signed-off-by: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
karthikbekalp
approved these changes
Apr 14, 2026
leon-li-inspire
approved these changes
Apr 14, 2026
This was referenced Apr 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a centralized
build-python-versionoutput (3.13) toreusable_tag_release.ymlso that downstream repos can reference it in theirPublishToPyPIjobs instead of hardcoding the Python version.Motivation
hatchling1.29.0 dropped Python 3.9 support (requires>=3.10). This broke thePublishToPyPIjob in repos still usingpython-version: '3.9'— e.g. deadline-cloud-test-fixtures run #41.By centralizing the build Python version here, we can update it in one place when build tools bump their requirements, rather than updating every repo individually.
Usage
Downstream repos reference it in their
PublishToPyPIjob:Repos that need updating
The following repos still have
python-version: '3.9'in theirPublishToPyPIjob:deadline-cloud-test-fixturesdeadline-cloud-worker-agentdeadline-cloud-for-nukedeadline-cloud-for-houdinideadline-cloud-for-3ds-maxdeadline-cloud-for-unreal-enginedeadline-cloud-for-vred